IBM 6611 CONFIGURATION TOOL PTF NP00688 NOTICE TO USERS

**********************************************************************
(C) COPYRIGHT International Business Machines Corp. 1992, 1993, 1994,
    1995, 1996. All Rights Reserved.
    Licensed Materials - Property of IBM.
**********************************************************************
FILE: README

This package of 4 diskettes contains the IBM Multiprotocol Network
Program (MPNP) Configuration Program, Version 1 Release 3.0 (V1R3), at
the PTF NP00688 level. PTF NP00688 contains a replacement for the MPNP
Configuration Program, V1R3, initially available on 9/94 and also replaces
PTF NP00372, NP00375, and NP00687.

PTF NP00688 contains configuration capabilities for all of the new
functions contained in IBM MPNP V1R3 PTF NP00387, and is therefore
required in order to run any of these functions. Please see item 20 in
this document for a description of the new functions.

INSTALLATION INSTRUCTIONS - Replacement:

Note:

If you operate 6611s at releases prior to V1R3, you must retain each
comparable matching level Configuration Tool version.

To install the 4 PTF NP00688 diskettes in a directory that currently
contains a copy of the Configuration Program, follow the installation
instructions in this README file. When prompted by the installation
program for the directory path of where the program will be installed,
enter the full path of the directory where your current version of the
Configuration Program is kept.

The installation process should not erase any files other than those
files that comprise the Configuration Program. For example, files
which have an extension of "cdb" will not be erased or modified.
(These files contain the configuration definitions created and saved
from within the Configuration Program using the Save or Save As...
functions in the File pull-down menu in the application menu bar.)
You should periodically back up the "cdb" files to ensure that you
always have current backup copies. Loss of the "cdb" files
would result in the loss of the configurations contained in the
files.


INSTALLATION INSTRUCTIONS - New installation:

To install the upgrade set of diskettes in a directory that
currently does not contain a copy of the Configuration Program
follow the installation instructions in this README file.


SUMMARY OF FIXES

This list summarizes the fixes included in this upgrade which have
been added since PTF NP00372.

NA01058 - Config program does not install on non-english AIX
          workstations
NA01197 - IPX SAP filter server name is not accepting underscores
NA01261 - Internal speed button of SDLC port does not remain
          highlighted
NA01262 - Change 'slow-poll' increments to tenths-of-a-second
NA01263 - Ranges should start at 1 not 0 for Net. Nums on IPX
          RIP filters
NA01264 - IPX/XNS/VINES port filters allow empty filters to be
          defined
NA01265 - Config not freeing up deleted Destination IP addresses
NA01266 - config should not validate if appn enabled and dlsw disabled
NA01267 - 'Activate CP-CP sessions' is a confusing label
NA01268 - Secondary SDLC Addr for 6611 only required when SDLC Addr
          is FF
NA01269 - Users of IBM6611 under Node Mgmt. lets duplicates be
          defined

This list summarizes the fixes included in this upgrade which were
originally availability in PTF NP00372.

NA01087 - On OS/2, LAN connected file systems return internal
          execution error
NA01091 - V1R2 config files fail to upgrade into V1R3 config program
NA01098 - Internal execution errors for Config Tool on OS/2 2.1
NA01100 - FR dest IP addrs cannot be used as APPN adj node or DLSw
          partners
NA01101 - No more checking TCP/UDP well-known port filters
NA01105 - Config Program does not work under AIX Japanese Locale
NA01106 - Blanked out fields not being saved correctly
NA01107 - config tool should limit max number bridged ports to 254
NA01108 - Nonfully Meshed IP Checking Changes
  1. Remove checking preventing a given DLCI from being
     associated with more than one IP addresses within the
     frame relay mesh. This will facilitate migration in that
     a customer can use their existing V1R2 configuration
     and re-configure for NFMFR at their leisure.

     Note that the checking to assure an IP address is only
     mapped to a single DLCI will remain.

  2. Remove the checking to assure the NFMFR destination
     addresses for FR virtual PPP links are within the same
     subnet as the local address (mesh address). This implies
     that valid host address checking must be done with the
     natural mask and that criteria germane to the subnet
     portion of the destination address are no longer
     applicable.

  3. For pull down lists and inter-port address checking, treat
     the Frame Relay virtual PPP Addresses as destination
     addresses rather than local addresses.
NA01109 - Recognize IBM 2210 configs in database files
NA01110 - Add subaddresses in ISDN call numbers
NA01119 - Editing OSPF interface gives dupiclate interface error msg
NA01133 - APPN shared storage can not be set to over 11 meg

PTF NP00688 also contains a correction for NA02333.

**********************************************************************
         I N S T A L L A T I O N   I N S T R U C T I O N S
**********************************************************************

This file contains additional documentation for the installation and
use of the IBM Multiprotocol Network Program Configuration Program
(referred to as the Configuration Program in this README file).  The
Configuration Program is used to configure an IBM 6611 Network
Processor (sometimes referred to as the 6611 in this README file).
This file should be read in its entirety with the exception of
sections marked optional.  Optional sections are also sometimes
provided in this file for miscellaneous purposes such as problem
resolution.

If you have a new IBM 6611 Network Processor you should read the
initial setup instructions sent with the machine.  Your IBM 6611
Network Processor is initialized with the Multiprotocol Network
Program Version 1 Release 3.0 (MPNP V1R3).  If all of your IBM
6611s were shipped with MPNP V1R3 preloaded on the hard file or if
all of your 6611s are being upgraded to use MPNP V1R3, this is the
correct version of this code.  There are incompatibilities in MPNP V1
configuration files, between R1.0 and R3, between R1.1/R1.2 and R3,
and between R2 and R3.

V1R3 of the Configuration Program is shipped on 4 diskettes
as opposed to the 3 diskettes in V1R2 and 5 diskettes in all
other prior releases.

***** NOTE ***** IMPORTANT ****** NOTE ***** IMPORTANT **********
This file pertains to V1R3 of the Configuration Program.  V1R3
of the Configuration Program will NOT configure an IBM 6611
Network Processor Release V1R1.0, Release V1R1.1/V1R1.2, or Release
V1R2. Therefore, if you have V1R1.0, V1R1.1/V1R1.2, or V1R2
level IBM 6611 Network Processors, you MUST retain your V1R1.0,
V1R1.1/V1R1.2, or V1R2 Configuration Program.
***** NOTE ***** IMPORTANT ****** NOTE ***** IMPORTANT **********

You should verify that you are using the correct release of the
Configuration Program to configure your IBM 6611 Network Processor.
To verify, check the title bar on the main screen of the Configuration
Program. If the release number is not on the title bar, then you have
V1R1.0 of the Configuration Program.

Each release of the Configuration Program configures a particular
release of the IBM 6611 Network Processor.  Refer to the
"History" section of this file to determine which release of the
Configuration Program to use to configure a given release of the
IBM 6611 Network Processor.

Refer to the IBM Multiprotocol Network Program Configuration
Guide, SC31-6691-01, for instructions on how to install and use the
Configuration Program.

Table of Contents:

        1.  Installation Files
        2.  Installation on a Microsoft Windows Workstation
        3.  Installation on an OS/2 2.1 Workstation
        4.  Installation on a RISC System/6000 Workstation
            Running AIX 3.1.5 or Later
        5.  Installing on a non-US English AIX Workstation
        6.  Troubleshooting problems starting on an AIX WorkStation
        7.  Fonts
        8.  Initialization Files
        9.  Using the Configuration Program with AIX NetView/6000
       10.  Configuration Samples
       11.  Other Files
       12.  IBM Xstation Setup
       13.  Deinstallation
       14.  History
       15.  Migrating Configuration Files to V1R3
       16.  Backward migration
       17.  Anonymous ftp site for IBM 6611 Network Processor
       18.  IP address and subnet mask validation (optional reading)
       19.  WAN Reroute - General Description
       20.  NP00688 Enhancements.

1.  Installation Files

Refer to the IBM Multiprotocol Network Program Configuration Guide
for instructions on how to install the Configuration Program.  When
you install the Configuration Program, several files will be copied
to the installation directory.  IT IS CRITICAL THAT YOU HAVE WRITE
PERMISSION TO THE INSTALLATION DIRECTORY TO INSTALL AND USE THE
CONFIGURATION PROGRAM.  THE CONFIGURATION PROGRAM WILL NOT RUN IF
YOU DO NOT HAVE WRITE PERMISSION TO THE INSTALLATION DIRECTORY.  The
Configuration Program writes the program files to the installation
directory during installation.  During program execution, the
Configuration Program writes to the installation directory such
information as the font and colors to use in the program.  The
Configuration Program also writes files to the installation directory
when creating or reading an IML diskette and in the event of an
"Internal execution error".  Additionally, the Configuration Program
can write files ending with the extension "cdb" to the installation
directory when saving a configuration.  These files are in binary
format and should not be changed via a file editor or with an AIX
command.

The following three lists contain the files that are installed in the
installation directory.  The first list is for AIX workstations, the
second list is for workstations running Microsoft Windows, and the
third list is for workstations running OS/2.

    AIX Windows workstations:
      README
      cfg.aix
      cfg.app
      cfg.hlp
      cfg.msg
      cfg
      cfg.ini (aix.ini on Configuration Program Diskette 1)
      cfg.lgo
      samples.cdb (optional)
      samples.doc (optional)

    Microsoft Windows 3.0 or 3.1 workstations:
      README
      cfg.exe
      cfg.app
      cfg.hlp
      cfg.msg
      cfg.ini (win30.ini or win31.ini on Configuration
               Program Diskette 1)
      cfg.lgo
      winmem32.dll
      samples.cdb (optional)
      samples.doc (optional)

    OS/2 2.1 workstations:
      README
      cfg.exe
      cfg.app
      cfg.hlp
      cfg.msg
      cfg.ini (os2.ini on Configuration Program Diskette 1)
      cfg.lgo
      samples.cdb (optional)
      samples.doc (optional)

2.  Installation on a Microsoft Windows Workstation

The Configuration Program is designed to run under Microsoft
Windows Version 3.0 or later in 386 Enhanced Mode.  The monitor
must have at least a 640x480 resolution with 16 colors or
greyscales.  To install the Configuration Program under Windows:

    1. Start Windows in Enhanced Mode by entering the following
       DOS command:  win /3

    2. After Windows is active, open the Run command dialog
       in Program Manager by selecting the File pulldown menu
       and then selecting Run on that menu.

    3. Insert Configuration Program Diskette 1 into the 3.5-inch
       diskette drive.  On the Run command
       dialog enter: A:\INSTALL.

       Note:  If your diskette drive is not assigned the letter A,
              substitute the letter assigned to your drive
              when you enter the command.

    4. Select Ok to execute the command.

The Configuration Program will install itself on the system and
will prompt you to enter the installation disk drive, directory,
group box name, and any other details necessary to complete the
installation.

3.  Installation on an OS/2 2.1 Workstation

The Configuration Program is designed to run under IBM OS/2
Version 2.1.  The monitor must have at least a 640x480 resolution
with 16 colors or greyscales.  To install the Configuration Program
under OS/2 2.1:

    1. Insert Configuration Program Diskette 1 into the 3.5-inch
       diskette drive.  At an OS/2 command prompt enter the
       command: A:\OS2INST.

       Note:  If your diskette drive is not assigned the letter A,
              substitute the letter assigned to your drive
              when you enter the command.

    2. Press Enter to execute the command.

The Configuration Program will install itself on the system and
will prompt you to enter the installation drive and directory.
An IBM 6611 folder will be created with the Configuration Program
icon inside.

4.  Installation on a RISC System/6000 Running AIX 3.1.5 or Later

The Configuration Program can run under AIX Version 3.1.5 and later
on a RISC System/6000 workstation.  The monitor must have at least a
640x480 resolution with 16 colors or greyscales.  As a part of its
installation and operation, the Configuration Program uses the
dosread, doswrite, dosdir and csh commands.  The Configuration
Program also uses these commands to read and write configurations to
a diskette.  These commands must be installed on the RISC System/6000
workstation before you install and use the Configuration Program.

Because of the way that the Configuration Program interfaces with
AIX Windows, sometimes Configuration Program windows are positioned
relative to the inside, upper-left corner of the window and not the
upper-left corner of the window border.

To correct this problem, add the following four lines to
your .Xdefaults file:

    Cfg6611.normal.mappingOffset: 11,27
    Cfg6611.transient.mappingOffset: 11,27
    Cfg6611.normal.configurationOffset: 0,0
    Cfg6611.transient.configurationOffset: 0,0

To install the Configuration Program on an AIX workstation:

    1. Insert Configuration Program Diskette 1 into the diskette
       drive.

    2. Enter the following commands in the sequence shown:
         dosread -a install.aix install.aix
         chmod 550 install.aix
         install.aix

    3. The last command, install.aix, starts the Configuration
       Program Installation, which will prompt you when to insert
       Diskettes 1 through 4.

5.  Installing on a non-US English AIX Workstation

If you are having trouble installing the Configuration Program on an
AIX workstation which does not have US English (LANG=En_US) set as the
default language you will need to open a new aixterm window with the
following command:

    aixterm -lang En_US

If this command does not work (ie - En_US is not installed on your
AIX workstation) then open a new aixterm window with the following
command:

    aixterm -lang C

Once you have the aixterm window open follow the normal instructions
for installing the Configuration Program.

6.  Troubleshooting problems starting on an AIX WorkStation

If you are trying to run the 6611 configuration program on a Risc
6000 and you are having problems getting the cfg script to work
properly, here are some things to check.

a) Do a hostname command to find out the hostname of the machine and
then ping the hostname. If you see '100% packet loss' after stopping
the ping command with Ctrl-C, then your tcpip setup is not correct.
A likely cause is the /etc/hosts file not having the correct IP
address on the first line that contains the hostname for the machine.
There can be other causes as well, but the bottom line is you need to
be able to ping the hostname of the machine successfully for the cfg
script to work without modification.

b) Do a df command to see if there are any key file systems like / or
/usr or /var that have close to 100% under the %used column. This also
can cause problems with the cfg script. The fix if one of your
filesystems is full is to go into smit and increase the size of your
filesystem.

c) You need to have write access to the directory that the cfg script
and associated files reside in.

d) If you have tried the above items and have not been successful as
of yet, then edit the cfg script. Once you are editing the cfg script,
search on the string 'checkDisplay'. (No quotes and with a capital D)
The first time you find it will be where the checkDisplay function is
defined. Comment out all of the lines starting with the line where
you see 'function checkDisplay {' and continuing until you see the
end of the function '}' mark in column one. (13 lines currently)
A comment line starts with # in column one. Search twice more for the
'checkDisplay' string, commenting each of those two lines out when
found.

7.  Fonts

The Configuration Program also requires specific X11
fonts.  When the Configuration Program starts up it looks in the
following subdirectory for the helvetica, times roman, and
new century schoolbook fonts:

   /usr/lib/X11/fonts/75dpi/helv*.Z
   /usr/lib/X11/fonts/75dpi/tim*.Z
   /usr/lib/X11/fonts/75dpi/ncen*.Z

Once the Configuration Program is running, it allows you to access
any font supported by your system. If an unusual font style, or very
large font size, is selected, you may lose the ability to read the
panels or make selections from them. Also, some fonts will hang the
Configuration Program under AIX 3.2.4. You can recover from font
problems by using one of the following procedures.

  a.Open the directory that contains the Configuration Program and
    edit the CFG.INI file.
      *Search for the line that reads FONTSIZE=xx(where xx is a font
       size) and change the parameter to FONTSIZE=14.
      *For AIX systems, search for the line that reads FONTFAMILY=xxx
       (where xxx is a font name) and change the parameter to
       FONTFAMILY=helvetica. For systems using Windows 3.1, change
       the parameter to FONTFAMILY=system.

  b.For AIX systems, locate the AIX.INI file on the Configuration
    Program diskettes. Copy this file to the directory that contains
    the Configuration Program and rename to file to CFG.INI. For
    Windows 3.1 systems, locate the WIN31.INI file on the
    Configuration Program diskettes. Copy this file to the directory
    that contains the Configuration Program and rename the file to
    CFG.INI.

8.  Initialization Files

The Configuration Program uses a user defaults file, cfg.ini,
to perform startup actions while loading the runtime image.
Although this file can be edited manually using a text editor
(such as vi), it is recommended that you make changes to the user
defaults file by using the dialogs Set font, Set Colors and
Set default model, found under the Options item in the Menu bar.
The cfg.ini file will be written when you press the Ok button.

If a cfg.ini file is not in the installation directory, the default
attributes will be used and the cfg.ini file will be re-created
using the defaults.

9.  Using the Configuration Program with AIX NetView/6000

The Configuration Program can run with AIX NetView/6000
on the AIX Windows workstation.  To properly configure
AIX NetView/6000 Version 1
for use with the Multiprotocol Network Program
(the software for the IBM 6611 Network Processor), append the
following lines in
/usr/etc/nm/registration/C/nodemgr

       #
       # MPNP Remote System Administration via TypeIII Application.
       #
       OVwApplication CFG TypeIII ARPA
       OVwMenu Administer
       OVwMenuItem Administer 'MPNP...'  1  Shared Computer 'cfg'
       OVwMenuItem Administer 'MPNP...'  1  Shared Gateway  'cfg'

If you have NetView/6000 Version 2, create the nodemgr file in the
/usr/OV/registration/C subdirectory with the following lines:

       /*
       **  Global Tools
       */


       Application "Config Tool"
       {
           Description {
                "6611 Config Tool"
           }

           /*
           **  Tools
           */

           MenuBar "Tools"
           {
           <1> "MPNP Configuration..."   _C   f.action "cfgtool";
           }

           Action "cfgtool"
           {
               Command "/usr/OV/bin/cfg.script";
           }

       }

In the /usr/OV/bin directory, create the cfg.script file with the
following lines:

       cd <full path name of the Configuration Tool directory>
       cfg

10. Configuration Samples

The Multiprotocol Network Program Configuration Guide (SC31-6691-01)
details many example configurations in chapter 5 and Appendix A.
These examples are also available for you to look at in the MPNP
Configuration Program in SAMPLES.CDB. There are 31 different example
types and 70 different configurations. Refer to the Multiprotocol
Network Program Configuration Guide (Chapter 5 and Appendix A) for
tables describing each parameter and value selected in the
configurations. Refer to SAMPLES.DOC for instructions on how to bring
up the samples while in the Configuration Program.

11. Other Files

Two files are currently created by the Configuration Program.  One
file, cfg.err on AIX systems, or CFG.ERR on DOS systems, is created
when an internal execution error occurs in the program.  This file
will contain the program stack at the time the error occurred.  The
contents of this file should be given to IBM support when a problem
with the Configuration program is reported.

Another file created by the Configuration Program is disk.inf.  This
file is only created on AIX systems and is used to contain information
about the internal processing that occurs when the Configuration
Program reads or writes an IML file to and from diskette.  The file
contains additional information and is only useful when a problem is
encountered reading and writing the IML file to and from the diskette
drive AND the Configuration Program has reported no errors.  This file
should be given to IBM support when reporting the problem with the IML
reading and writing process.

NOTE: The above mentioned files are written to the directory from
which the Configuration Program was started.

12. IBM Xstation Setup

The monitor must have at least 640 x 480 resolution with 16
colors or greyscales.  In order to run the Configuration Program
from an IBM Xstation which is connected to an IBM RISC
System/6000 host, you need to have /usr/lib/X11/fonts/75dpi/
directory in the Font Path of your Xstation.  You can check to
see if this directory is already in your path by typing:

     xset -q

Under Font Path, look for /usr/lib/X11/fonts/75dpi/ in the list of
directories.

If you do not have this directory in your Xstation Font Path then from
your Xstation type:

     xset fp+ /usr/lib/X11/fonts/75dpi/

This will add the Configuration Program font directory to your
Xstation Font Path. For future use of the Configuration Program
through Xstations, place the above line in your .profile.

NOTE: If your font path is not set correctly, you may get an "out of
memory" error message.

13. Deinstallation

To de-install the Configuration Program, it is recommended that
all files ending in cdb in the installation directory be saved.
These files contain configurations that have been saved by the
Configuration Program when the "Save" or "Save As" dialogs were
executed.  After making backup copies of all the cdb files, all the
files in the installation directory can be removed using the rm
command on AIX or using the del command on DOS or OS/2.  On AIX
systems, the .Xdefaults file may contain 4 lines of definitions as
defined in section 2 in this README file.  Those 4 lines in the
.Xdefaults can be removed using an editor such as vi.

14. History

Listed below are the versions of the Configuration Program with
the version of the IBM 6611 Network Configuration Processor they can
configure. If you are not sure which version of the Configuration
Program you have, check the title bar on the main screen of the
Configuration Program. If it is not displayed there, then you have
Configuration Program V1R1.0.

   * Configuration Program V1R1.0
        IBM 6611 Network Processor V1R1.0

   * Configuration Program V1R1.1
        IBM 6611 Network Processor V1R1.1

   * Configuration Program V1R1.1.2
        IBM 6611 Network Processor V1R1.1.2

   * Configuration Program V1R2
        IBM 6611 Network Processor V1R2

   * Configuration Program V1R3
        IBM 6611 Network Processor V1R3

15. Migrating Configuration Files to V1R3

The configuration formats for V1R1.0, V1R1.1/V1R1.2, V1R2, and V1R3
are not compatible.  If you want to use configuration files created
using MPNP V1R1.0, V1R1.1/V1R1.2, or V1R2, you must migrate the
configuration files to V1R3.

The Configuration Program converts the configuration files
automatically when you read them from diskette, from your workstation,
or when you retrieve them from an active 6611 using the the
Communicate function of the Configuration Program.  When migrating,
do not use System Manager to create your first MPNP V1R3
configuration file.  You must use the MPNP V1R3 Configuration Program
to convert old version configuration files to produce your new
MPNP V1R3 configuration files.

It is recommended that you create a back up of each configuration file
BEFORE you convert it to the V1R3 format. After a configuration file
is converted to the new format, the V1R1.0, V1R1.1/V1R1.2, and V1R2
MPNP and its IBM Multiprotocol Network Program Configuration Program
will not be able to read the file.  Once configuration files have been
migrated to a newer release, there is no way to convert these files
back to their original release.

The old version configuration files that you are converting might
exist in one of three places:

a)  On diskette
b)  In the 6611
c)  In a configuration database (*.cdb) on the configuration
    workstation

If there are MPNP V1R1.0, V1R1.1, V1R1.2, and V1R2 configuration files
that exist only in the 6611, save them on diskette before you upgrade
the MPNP code in the 6611 to the V1R3 level.  At least two copies of
each needed configuration should be saved.  One copy is converted to
the MPNP V1R3 format and the other is saved for backup purposes.

a) Converting Configuration Files from Diskette

   Follow these steps to convert configuration files from diskette:

   1.  From the menu bar of the V1R3 Configuration Program, select the
       CONFIGURE pull-down and then select READ CONFIGURATION
       DISKETTE. The Configuration Program displays a warning message
       to indicate that the configuration being loaded from the
       diskette is an old version and enables you to continue or
       cancel the conversion.

       NOTE: You can set message prompting to disable the display of
       messages when upgrading previous level configuration files.
       Select the OPTIONS pull-down from the menu bar, and then select
       MESSAGE PROMPTING. Disable the Upgrade of previous level
       configuration files parameter.

   2.  Determine whether the 6611 for which the configuration file is
       destined will be upgraded to V1R3 or has already been upgraded
       to V1R3 and do one of the following:

       -   When the configuration file is destined for a 6611 which
           will be upgraded to V1R3, configure the Schedule
           Configuration option. From the main menu, select NODE
           MANAGEMENT and then select SCHEDULE CONFIGURATION.  On the
           Schedule Configuration window, set the Apply configuration
           parameter to AT UPGRADE and set the Source release
           parameter to the release of MPNP before the upgrade is
           applied.  The V1R3 configuration is activated after the
           6611 had been upgraded to V1R3.
       -   When the configuration file is destined for a 6611  which
           has already been upgraded to V1R3, do NOT configure the
           Schedule Configuration option.  The configuration file is
           applied immediately.

   3.  Select the CONFIGURE pull-down and then select CREATE
       CONFIGURATION DISKETTE.  When the diskette is complete, take it
       to the 6611 that is being upgraded to V1R3.

b) Converting Configuration Files Retrieved from an Active 6611

   Follow these steps to convert configuration files retrieved from
   an active 6611:

   1.  From the menu bar of the V1R3 Configuration Program, select the
       COMMUNICATE pull-down, and then select RETRIEVE and select the
       CONFIGURATION or CURRENT CONFIGURATION option.  The
       Configuration Program displays a warning message to indicate
       that the configuration being loaded from the diskette is an
       old version and enables you to continue or cancel the
       conversion.

       NOTE: You can set message prompting to disable the display of
       messages when upgrading previous level configuration files.
       Select the OPTIONS pull-down from the menu bar, and then select
       MESSAGE PROMPTING. Disable the Upgrade of previous level
       configuration files parameter.

       NOTE:  The 6611 may display a C73 error code as the
       Configuration Program attempts communication with the 6611
       using V1R3 type messages before using V1R1.0, V1R1.1/V1R1.2, or
       V1R2 type messages. This condition is normal when using the
       V1R3 Configuration Program to communicate with an older version
       of the MPNP.

   2.  Determine whether the 6611 for which the configuration file is
       destined will be upgraded to V1R3 or has already been upgraded
       to V1R3 and do one of the following:

       -   When the configuration file is destined for a 6611 which
           will be upgraded to V1R3, configure the Schedule
           Configuration option. From the main menu, select NODE
           MANAGEMENT and then select SCHEDULE CONFIGURATION.  On the
           Schedule Configuration window, set the Apply configuration
           parameter to AT UPGRADE and set the Source release
           parameter to the release of MPNP before the upgrade is
           applied.  The V1R3 configuration activates after the 6611
           had been upgraded to V1R3.
       -   When the configuration file is destined for a 6611  which
           has already been upgraded to V1R3, do NOT configure the
           Schedule Configuration option.  The configuration file is
           applied immediately.

   3.  Select the CONFIGURE pull-down, and then select the SAVE option
       and then select SAVE AND VALIDATE.

       NOTE: Configuration files must be validated when you use the
       Send multiple configurations function of the Configuration
       Program to send configuration files to the 6611.  When you try
       to send files that have not been validated, a warning message
       appears and the file is not sent.

   4.  To send converted configuration files back to the 6611s, select
       the COMMUNICATE pull-down, and then select SEND and select the
       CURRENT CONFIGURATION or MULTIPLE CONFIGURATIONS option.

c) Converting Multiple Configuration Files from a Configuration
   Database

   Follow these steps to convert one or more configuration files from
   a configuration database:

   1.  Determine whether you want the Configuration Program to prompt
       you for each configuration file as it is converted.

       To disable message prompting from the menu bar of the V1R3
       Configuration Program, select OPTIONS pull-down from the menu
       bar, and then select MESSAGE PROMPTING.  Disable the Upgrade of
       previous level configuration files parameter.  Then select OK.

   2.  Determine whether you want the Configuration Program to
       automatically validate each configuration file when copying
       from the configuration database.

       NOTE: Configuration files must be validated when you use the
       Send multiple configurations function of the Configuration
       Program to send configuration files to the 6611.  When you try
       to send files that have not been validated, a warning message
       appears and the file is not sent.

       To enable automatic validation, select the OPTIONS pull-down
       and then select the VALIDATION option.  The Validation window
       appears. Enable the Copying database configuration(s) parameter
       and then select OK.

   3.  Select the CONFIGURE pull-down and then select COPY DATABASE
       CONFIGURATION(S).  The Copy Database Configuration(s) window
       appears. Determine whether to copy one configuration or
       multiple configurations and do one of the following:

       -   To copy one configuration:

           a.  Select the origin database file and the configuration
               to be copied.

           b.  Specify the destination database file that will receive
               the configuration, or select the database file from the
               list of databases displayed.

           c.  Specify the destination name of the configuration file
               being copied or select a file name from the list of
               configurations displayed.

       -   To copy multiple configurations:

           a.  Select the origin database file and the configurations
               to be copied.  Selected configuration file names are
               highlighted.

           b.  Specify the destination database file that will receive
               the configurations, or select the database file from
               the list of databases displayed.  The Configuration
               name parameter is not available.

   4.  Determine how to transport the configuration files to the 6611s
       that are being upgraded the V1R3 and then transport the files.

16.  Backward Migration is not supported. Once configuration files
     have been migrated to a newer release there is no way to convert
     these files back to their original release.

17. Anonymous ftp site for IBM 6611 Network Processor

    IBM has established an anonymous ftp site for providing
    information and configuration program updates (and in the future
    other program updates) relating to the 6611.

    The hostname for the anonymous ftp site is nways.raleigh.ibm.com.
    If you have trouble resolving this name the IP address is
    192.35.236.5. After connecting to the machine specify
    anonymous as the user id and your e-mail address as your
    password. Check the README file on the anonymous ftp site
    in the /pub directory for the latest information.

18. IP address and subnet mask validation

  This section describes the IBM 6611 Configuration Program checking
  required to validate IP addresses and masks.  Some of these checks
  apply to the IP address field alone, some apply to the Sub Net Mask
  alone, and some apply to the IP field in conjunction with the Sub
  Net Mask field. The most complicated checks apply to a specified IP
  address, an IP address on an interface, the mask at the same
  interface and the natural mask. Each Criteria will explain what
  values are being used in the validation.

  Throughout this section IP addresses will be refered to in the
  standard dotted decimal form of B0.B1.B2.B3 . It is assumed that the
  reader knows how to convert this notation to both hexadecimal and
  binary notations.

  Example

  DOTTED DECIMAL      9.67.128.33
  HEXADECIMAL         X'09' X'43' X'80' X'21'
  BINARY              B'00001001' B'01000011' B'10000000' B'00100001'

  Reference will also be made to the the class of service which is
  defined as follows:

  CLASS A - (1 <= B0 <= 127)         B0 = Network Address, B1.B2.B3 =
                                     Host Address
  CLASS B - (128 <= B0 <= 191)       B0.B1 = Network Address, B2.B3 =
                                     Host Address
  CLASS C - (192 <= B0 <= 223)       B0.B1.B2 = Network Address, B3 =
                                     Host Address

  The natural network masks based on the class of service are defined
  as follows:

  o   Class A - 255.0.0.0
  o   Class B - 255.255.0.0
  o   Class C - 255.255.255.0



  EDUCATION
  _________


  NETWORK + SUBNET

  How to get the Network + Subnet portion of an IP address with mask.

  Perform logical AND across all bits:

  MASK -           B'111111...000000'
  IP ADDRESS -     B'xxxxxx...xxxxxx'
                   -----------------------
                   B'xxxxxx...000000' (x's represent the Net + Subnet)

  HOST ID

  How to get the Host ID portion of an IP address with mask.

  1.  Invert mask bits.

      MASK -           B'111111...000000'
      INVERTED MASK -  B'000000...111111'

  2.  Perform logical AND across all bits:

      INVERTED MASK -  B'000000...111111'
      IP ADDRESS -     B'xxxxxx...xxxxxx'
                       -----------------------
                       B'000000...xxxxxx' (x's represent the Host ID)

  NETWORK

  How to get the Network portion of an IP address with natural mask.

  NOTE:  If no mask is associated with an IP address, the natural mask
  is be used.

  o   Class A.

      Perform logical AND across all bits:

      NATURAL MASK -   '255.0.0.0'
      IP ADDRESS -     'B0.B1.B2.B3'
                       ------------------
                       'B0.0.0.0' (B0 represents the Network)

  o   Class B.

      Perform logical AND across all bits:

      NATURAL MASK -   '255.255.0.0'
      IP ADDRESS -     'B0.B1.B2.B3'
                       ------------------
                       'B0.B1.0.0' (B0.B1 represents the Network)

  o   Class C.

      Perform logical AND across all bits:

      NATURAL MASK -   '255.255.255.0'
      IP ADDRESS -     'B0.B1.B2.B3'
                       ------------------
                       'B0.B1.B2.0' (B0.B1.B2 represents the Network)

  SUBNET

  How to get the Subnet portion of an IP address with mask.  First,
  get Network + Subnet portion by clearing all host bits (see
  "Network + Subnet").

  o Class A.

    Perform logical AND across all bits:

    INVERT NATURAL MASK - X'00FFFFFF'
    NETWORK + SUBNET -    B'xxxxxx...000000'
                          -----------------------
                          '000...xxx...000' (x's represent the Subnet)

  o Class B.

    Perform logical AND across all bits:

    INVERT NATURAL MASK - X'0000FFFF'
    NETWORK + SUBNET -    B'xxxxxx...000000'
                          ------------------------
                          '000...xxx...000' (x's represent the Subnet)

  o Class C.

    Perform logical AND across all bits:

    INVERT NATURAL MASK - X'000000FF'
    NETWORK + SUBNET -    B'xxxxxx...000000'
                          ------------------------
                          '000...xxx...000' (x's represent the Subnet)

  QUESTION CHECKS
  _______________

  This section deals with question level checking which can be applied
  to a single IP address and an IP address and mask.  In the cases
  where a mask is required, the question corresponding to the mask
  will be identified.

  INVALID IP ADDRESSES

  o   Class A

      INVALID ADDRESSES        EXAMPLES
      0.X.X.X                  0.128.105.3
      127.X.X.X                127.128.105.3

  o   Class C

      INVALID ADDRESSES        EXAMPLES
      B0 (224 - 255)           224.128.105.3
                               235.128.105.3
                               255.128.105.3

  This applies to 'PANEL' questions:

  1.  'SNA DLSw' IP address of destination router
  2.  'APPN Adjacent Node' Link Station - Detail
  3.  'BGP Group - Detail' Next hop destination
  4.  'BGP Group - Detail' Interface IP Address
  5.  'BGP Unconfigured Neighbor - Detail' IP address
  6.  'BGP Configured Neighbor - Detail' BGP neighbor IP address
  7.  'BGP Configured Neighbor - Detail' Next hop destination
  8.  'BGP Configured Neighbor - Detail' Interface IP address
  9.  'BGP Import Destination - Detail' Destination
  10. 'Configuration Hosts' IP address
  11. 'DLSw Partners' IP address of remote 6611 router
  12. 'DLSw' Default DLSw IP address for this 6611
  13. 'EGP Neighbor Detail' EGP neighbor IP address
  14. 'EGP Group Options' Next hop address or domain name
  15. 'EGP Import Destination - Detail' Destination
  16. 'Export Filter - Detail' Export destination
  17. 'IP Routing - OSPF' Router ID
  18. 'Virtual Link - Detail' Virtual neighbor ID
  19. 'Network Ranges' Network number
  20. 'OSPF Neighbor - Detail' IP address of neighbor router
  21. 'OSPF Interface - Detail' Interface IP address
  22. 'HELLO Interface - Detail' IP address of local interface
  23. 'HELLO Trusted Routers' IP address of trusted router
  24. 'HELLO Source Routers' IP address of source router
  25. 'HELLO Import Destination - Detail' Destination
  26. 'HELLO Import Interface - Detail' IP address of local interface
  27. 'HELLO Import Routers' IP address of remote router
  28. 'Static Route - Detail' Destination address
  29. 'Static Route - Detail' Next hop router number 1
  30. 'Static Route - Detail' Next hop router number 2
  31. 'Static Route - Detail' Next hop router number 3
  32. 'NetBIOS DLSw' IP address of destination router
  33. 'RIP Interface - Detail' IP address of local interface
  34. 'RIP Trusted Routers' IP address of trusted router
  35. 'RIP Source Routers' IP address of source router
  36. 'RIP Import Destination - Detail' Destination
  37. 'RIP Import Interfaces - Detail' IP address of local interface
  38. 'RIP Import Routers' IP address of remote router
  39. 'Remote Hosts' IP address of host
  40. 'Time Servers' IP address of remote time server
  41. 'SNMP Community - Detail' Community address (IP address or
      Domain name)
  42. 'Trap address (IP address or Domain name)' SNMP Client - Detail
  43. 'Ethernet Port - IP', 'Serial Port - IP over Frame Relay',
      'Serial Port - IP over PPP', 'Serial Port - IP over SMDS',
      'Token Ring Port - IP', 'X.25 Port - IP' IP Address, 'I-I/F BRI
      Port - IP'
  44. 'Serial Port - IP over PPP' Destination IP address
  45. 'IP Destination - Detail' Destination IP address
  46. 'IP Point-to-Point Address - Detail' IP point-to-point
      destination
  47. 'X.25 Remote Host - Detail' Destination IP address for X.25

  HOST BITS NOT ALL 1'S

  Check that the Host portion of the address is not all 1's using the
  natural network mask. This applies to the same questions as "Invalid
  IP addresses".

  HOST BITS ZERO USING NATURAL MASK

  Check that when using the natural mask the host bits are non-zero.

  This applies to 'PANEL' questions:

  1.  'SNA DLSw' IP address of destination router
  2.  'APPN Adjacent Node' Link Station - Detail
  3.  'BGP Group - Detail' Next hop destination
  4.  'BGP Group - Detail' Interface IP Address
  5.  'BGP Configured Neighbor - Detail' BGP neighbor IP address
  6.  'BGP Configured Neighbor - Detail' Next hop destination
  7.  'BGP Configured Neighbor - Detail' Interface IP address
  8.  'DLSw Partners' IP address of remote 6611 router
  9.  'DLSw' Default DLSw IP address for this 6611
  10. 'EGP Neighbor Detail' EGP neighbor IP address
  11. 'EGP Group Options' Next hop address or domain name
  12. 'IP Routing - OSPF' Router ID
  13. 'Virtual Link - Detail' Virtual neighbor ID
  14. 'OSPF Neighbor - Detail' IP address of neighbor router
  15. 'OSPF Interface - Detail' Interface IP address
  16. 'HELLO Interface - Detail' IP address of local interface
  17. 'HELLO Trusted Routers' IP address of trusted router
  18. 'HELLO Source Routers' IP address of source router
  19. 'HELLO Import Interface - Detail' IP address of local interface
  20. 'HELLO Import Routers' IP address of remote router
  21. 'Static Route - Detail' Next hop router number 1
  22. 'Static Route - Detail' Next hop router number 2
  23. 'Static Route - Detail' Next hop router number 3
  24. 'NetBIOS DLSw' IP address of destination router
  25. 'RIP Interface - Detail' IP address of local interface
  26. 'RIP Trusted Routers' IP address of trusted router
  27. 'RIP Source Routers' IP address of source router
  28. 'RIP Import Interfaces - Detail' IP address of local interface
  29. 'RIP Import Routers' IP address of remote router
  30. 'Remote Hosts' IP address of host
  31. 'Time Servers' IP address of remote time server
  32. 'Trap address (IP address or Domain name)' SNMP Client - Detail
  33. 'Ethernet Port - IP', 'Serial Port - IP over Frame Relay',
      'Serial Port - IP over PPP', 'Serial Port - IP over SMDS',
      'Token Ring Port - IP', 'X.25 Port - IP' IP Address, 'I-I/F BRI
      Port - IP'
  34. 'Serial Port - IP over PPP' Destination IP address
  35. 'IP Destination - Detail' Destination IP address
  36. 'IP Point-to-Point Address - Detail' IP point-to-point
      destination
  37. 'X.25 Remote Host - Detail' Destination IP address for X.25

  NETWORK IP CHECK WITH SPECIFIED MASK

  In this check, the host portion of the address is checked to assure
  that it is zero.  In all cases where this check is requested, a mask
  is specified. Note that the case where the mask is all 1's (Host
  Address) should be allowed.

  This applies to questions:

  1.  BGP Unconfigured Neighbors
          'BGP Unconfigured Neighbor - Detail' IP address
          'BGP Unconfigured Neighbor - Detail' Mask
  2.  BGP Import Filter
          'BGP Import Destination - Detail' Destination
          'BGP Import Destination - Detail' Destination mask
  3.  Configuration Station Address Range
          'Configuration Hosts' IP address
          'Configuration Hosts' Address mask
  4.  EGP Import Filter
          'EGP Import Destination - Detail' Destination
          'EGP Import Destination - Detail' Destination mask
  5.  Export Filter
          'Export Filter - Detail' Export destination
          'Export Filter - Detail' Mask
  6.  OSPF Area Network Range
          'Network Ranges' Network number
          'Network Ranges' Network mask
  7.  HELLO Import Filter
          'HELLO Import Destination - Detail' Destination
          'HELLO Import Destination - Detail' Destination mask
  8.  IP Static Route Destination
          'Static Route - Detail' Destination address
          'Static Route - Detail' Destination mask
  9.  Rip Import Filter
          'RIP Import Destination - Detail' Destination
          'RIP Import Destination - Detail' Destination mask
  10. SNMP Community Domain (when interpreted as IP address)
          'SNMP Community - Detail' Community address
          'SNMP Community - Detail' Community address mask

  HOST IP ADDRESS CHECK WITH MASK

  In this check, the host portion of the IP address is checked to
  assure that it is non-zero.

  For port level questions the criteria can be applied since the mask
  is known:

  1.  Port IP Address
          'Ethernet Port - IP', 'Serial Port - IP over Frame Relay',
          'Serial Port - IP over PPP', 'Serial Port - IP over SMDS',
          'Token Ring Port - IP', 'X.25 Port - IP', 'I-I/F BRI
          Port - IP' IP Address 'Ethernet Port - IP', 'Serial Port -
          IP over Frame Relay', 'Serial Port - IP over PPP', 'Serial
          Port - IP over SMDS', 'Token Ring Port - IP', 'X.25 Port -
          IP', 'I-I/F BRI Port - IP' Subnet mask
  2.  Port IP Destination Address
          'Serial Port - IP over PPP' Destination IP address
          'Serial Port - IP over PPP' Subnet mask
  3.  Port X.25 Destination Address
          'X.25 Remote Host - Detail' Destination IP address for X.25
          'X.25 Remote Host - Detail' Subnet mask
  4.  Port Frame Relay DLCI IP Destination Address
          'IP Destination - Detail' Destination IP address
          'IP Destination - Detail' Subnet mask
  5.  Port Frame Relay IP Point-to-Point Destination Address
          'IP Point-to-Point Address - Detail' IP point-to-point
          destination

  KEYWORD 'ALL' VALID

  ALL is valid for the following questions:

  1.  'BGP Unconfigured Neighbor - Detail' IP address
  2.  'BGP Import Destination - Detail' Destination
  3.  'EGP Import Destination - Detail' Destination
  4.  'Configuration Hosts' IP address
  5.  'Export Filter - Detail' Export destination
  6.  'HELLO Import Destination - Detail' Destination
  7.  'RIP Import Destination - Detail' Destination

  KEYWORD 'DEFAULT' IS VALID

  Default is valid for the following questions:

  1.  'BGP Import Destination - Detail' Destination
  2.  'EGP Import Destination - Detail' Destination
  3.  'Export Filter - Detail' Export destination
  4.  'HELLO Import Destination - Detail' Destination
  5.  'RIP Import Destination - Detail' Destination
  6.  'Static Route - Detail' Destination address

  Prior to MPNP V1R2, specification of 0.0.0.0 as an IP address is a
  valid means of specifying default in the Config Tool. With V1R2 and
  higher, the user will have a single radio-button to specify default.
  Upgrade of previous configurations will be transparent given that
  customers follow the installation procedures.

  LOOPBACK IP ADDRESS

  This is invalid for the same questions as "Invalid IP addresses"
  with the exception that loopback (127.0.0.1) can be specified for:

  1.  'Static Route - Detail' Next hop router number 1

  NOTE:  Limitation of the loopback address is to the first next hop
  address.

  CONTIGUOUS BITS IN MASK

  The 1's in all masks must be left justified and contiguous. This
  applies to:

  1.  'BGP Unconfigured Neighbor - Detail' Mask
  2.  'BGP Import Destination - Detail' Destination mask
  3.  'Configuration Hosts' Address mask
  4.  'Export Filter - Detail' Mask
  5.  'EGP Import Destination - Detail' Destination mask
  6.  'HELLO Import Destination - Detail' Destination mask
  7.  'Static Route - Detail' Destination mask
  8.  'Network Ranges' Network mask
  9.  'RIP Import Destination - Detail' Destination mask
  10. 'IP Destination - Detail' Subnet mask
  11. 'SNMP Community - Detail' Community address mask

  ALL 0'S NOT A VALID MASK

  This applies to the same questions as "Contiguous Bits in mask."

  MINIMUM NUMBER OF MASK BITS

  The same questions as "Contiguous Bits in mask."

  SUBNET RULES

  This check assures the subnet portion of the IP address cannot be
  all 1's or all 0's. Note that this implies that the subnet portion
  of the IP must be at least 2 bits in length.  This criteria applies
  to the same questions as "Contiguous Bits in mask."

  NO OVERLAPPING SUBNETS

  For two interfaces on the same network, an overlapping subnet occurs
  when a partial subnet of one interface is equal to the total subnet
  of another interface.

  Example

  First interface - IP address 128.8.105.1 Subnet mask - 255.255.240.0

  Second interface - IP address 128.8.104.1 Subnet mask -
  255.255.252.0

  o First interface (Class B)

    IP ADDRESS -      B'10000000 00001000 01101001 00000001'
    SUBNET MASK -     B'11111111 11111111 11110000 00000000' (Bit AND)
                      ------------------------------------------------
    NET + SUBNET -    B'10000000 00001000 0110

    NATURAL MASK -    B'11111111 11111111 00000000 00000000'
    INVERT NAT MASK - B'00000000 00000000 11111111 11111111'

    NET + SUBNET -    B'10000000 00001000 0110
    INVERT NAT MASK - B'00000000 00000000 11111111 11111111' (Bit AND)
                      ------------------------------------------------
    SUBNET -                              0110

  o Second interface (Class B)

    IP ADDRESS -      B'10000000 00001000 01101000 00000001'
    SUBNET MASK -     B'11111111 11111111 11111100 00000000' (Bit AND)
                      ------------------------------------------------
    NET + SUBNET -    B'10000000 00001000 011010

    NATURAL MASK -    B'11111111 11111111 00000000 00000000'
    INVERT NAT MASK - B'00000000 00000000 11111111 11111111'

    NET + SUBNET -    B'10000000 00001000 011010
    INVERT NAT MASK - B'00000000 00000000 11111111 11111111' (Bit AND)
                      ------------------------------------------------
    SUBNET -                              011010

  Since the natural nets are the same (128.8) and the longer subnet
  overlaps the shorter, this is an example of overlapping subnets.

  This check is applicable to the following port IP address
  questions:
      'Ethernet Port - IP', 'Serial Port - IP over Frame Relay',
      'Serial Port - IP over SMDS', 'Token Ring Port - IP', 'X.25
      Port - IP', 'I-I/F BRI Port - IP' IP Address
      'Ethernet Port - IP', 'Serial Port - IP over Frame Relay',
      'Serial Port - IP over SMDS', 'Token Ring Port - IP', 'X.25
      Port - IP', 'I-I/F BRI Port - IP' Subnet mask

  ALL ONES INVALID SUBNET MASK

  255.255.255.255 is an invalid subnet mask on all port IP interface
  specifications except for PPP.

  This check is applicable to the following subnet mask questions:
      'Ethernet Port - IP', 'Serial Port - IP over Frame Relay',
      'Serial Port - IP over SMDS', 'Token Ring Port - IP', 'X.25
      Port - IP', 'I-I/F BRI Port - IP' Subnet mask

  SAME NETWORK

  1.  In 'BGP Group - Detail' screen the Interface IP address must be
      on the same network as the Next hop address. This is also true
      for the 'BGP Configured Neighbor - Detail' screen.
  2.  In 'OSPF Interface - Detail' screen the Interface IP address
      must be on the same network as the IP address of Neighbor router
      on the 'OSPF Neighbor - Detail' screen.
  3.  In 'Serial Port - IP over PPP' screen the Destination IP address
      must be on the same network as the IP address.  This check is
      not applied if the destination mask is 255.255.255.255.
  4.  In 'IP Destination per DLCI - Detail' screen under Frame Relay
      the Destination IP address must be on the same network as the IP
      address in the 'Serial Port - IP over Frame Relay' screen.
  5.  In 'IP Point-to-Point Address - Detail' screen under Frame Relay
      the IP point-to-point destination must be on the same network as
      the IP address in the 'Serial Port - IP over Frame Relay'
      screen.
  6.  In 'X.25 Remote Host - Detail' screen the Destination IP address
      for X.25 must be on the same network as the IP address in the
      'X.25 Port - IP' screen.

  INTER-QUESTION CHECKS
  _____________________

  This section documents the inter-question checking which needs to be
  done prior to storing a configuration.

  IP ADDRESS MUST BE ON A DIRECTLY ATTACHED NETWORK

  This check implies that the specified address must correspond to a
  directly attached interface. In other words, the IP address when
  AND'ed with the port mask must equal the port address AND'ed with
  the same mask for one of the ports.

  This check applies to the following questions:

  1.  'EGP Group Options' Next hop address or domain name
  2.  'HELLO Trusted Routers' IP address of trusted router
  3.  'HELLO Source Routers' IP address of source router
  4.  'HELLO Import Routers' IP address of remote router
  5.  'RIP Trusted Routers' IP address of trusted router
  6.  'RIP Source Routers' IP address of source router
  7.  'RIP Import Routers' IP address of remote router
  8.  'OSPF Neighbor - Detail' IP address of neighbor router
  9.  'BGP Group - Detail' Next hop destination
  10. 'BGP Configured Neighbor - Detail' Next hop destination
  11. 'Static Route - Detail' Next hop router number 1
  12. 'Static Route - Detail' Next hop router number 2 multi-path
      route

  IP ADDRESS MUST BE LOCAL ADDRESS

  This is simply a check to assure that the address is one of the
  configured interfaces. In other words, the IP address must equal
  either a port IP address, a port IP point-to-point destination
  address on Frame Relay, or a port destination IP address on PPP.

  In most cases, these questions only allow specification on a
  configured interface. However, the check is required to allow
  proliferation of port configuration changes:

  1.  'HELLO Import Interface - Detail' IP address of local interface
  2.  'RIP Import Interfaces - Detail' IP address of local
  3.  'OSPF Interface - Detail' Interface IP address
  4.  'RIP Interface - Detail' IP address of local interface
  5.  'HELLO Interface - Detail' IP address of local
  6.  'From Interface/Gateway' IP address of local interface
  7.  'To Interface/Gateway' IP address of local interface

  Additionally, the following question must correspond to a local
  address.

  1.  'DLSw' Default DLSw IP address for this 6611
  2.  'IP Routing - OSPF' Router ID
  3.  'BGP Group - Detail' Interface IP Address
  4.  'BGP Configured Neighbor - Detail' Interface IP address

  NOTE: Prior to V1R3 the two BGP Interface IP Addresses used the port
  destination IP address on PPP ports which was incorrect.  When
  upgrading configurations to V1R3 if port destination IP addresses on
  PPP ports are defined for the BGP IP Addresses, the corresponding
  local IP addresses on those PPP ports will be used instead.

19. WAN Reroute - General Description

WAN Reroute support gives the 6611 the ability to be the
receiver of a dial-in link that backs up a failed WAN
link. It also gives the 6611 the ability to be the
caller for backing up a failed leased WAN link.  The 6611
can detect the outage of a single WAN Frame Relay port
and be able to establish a PPP link (via external
programable modem) to a remote site to back up this
failed Frame Relay link.  This is a single one-to-one
relationship in any one 6611 router. There can be no more
than one FR port backed up and one PPP backup port. On
the PPP backup port the modem must have the capability of
being programmed with the remote site phone number it is
to connect to, as the router will NOT send a phone number
to it, but only raise DTR when the backup connection is
desired and lower DTR when the connection is no longer
needed.

The configuration of WAN Reroute is done only on the
dial-out side of the WAN reroute link. The configuration
is on the port level of FR and PPP ports under Physical
-- click on Dial backup and the screen is shown for
entering the parameters.

WAN Reroute lets the user configure --

   o   which single WAN PPP port is designated the backup
       port.

   o   which single WAN FR port is to be backed up in case
       of failure.

   o   length of time WAN port being backed up (when it
       comes back up) is up continuously before the dial
       backup connection is disconnected (called stability
       time).

WAN Reroute does the following --

   o   monitor the candidate WAN port for its up/down status
       change.

   o   once a WAN port failure is detected, have the backup
       port establish a switched connection by having the
       adapter raise DTR to the modem so it will dial its
       preprogrammed phone number(s).

   o   if the failed WAN link becomes operational ('up')
       again, disconnect the corresponding backup link once
       the FR port stays up continuously for the stability-
       time duration.

Once a backup dial link is connected to the target host
the Phase-1 functions will take care of starting IP/IPX
traffic flow over this backup link.   Likewise, once the
failed FR link becomes operational again the Phase-1
functions will take care of stopping IP/IPX traffic from
coming over the backup link and start IP/IPX traffic
flowing over the primary link.

WAN Reroute Limitations

   o   The backup port must have a unique local IP address,
       different from the FR port it is intended to back up.

   o   The backup port and all its potential target host(s)
       must be in the same IP subnet if connecting to a 2210
       or Cisco router; that is, they share the same IP
       network portion of IP address. This is not so if the
       connection is to another 6611.

20. NP00688 Enhancements

The 6611 Config Tool now allows IP supernets to be configured.
Previously, checks were performed to assure that the IP mask was
equal or more specific than the mask implied by the class of
the IP address. For example, the least specific mask which could
be specified for the IP net (192.5.224.0) was 255.255.255.0.
MPNP V1R3 PTF NP00387 is required to exploit this capability.

Additionally, the 6611 Config Tool will no longer issues a warning
message when an all 0's or all 1's subnet is specified. For example,
192.1.1.1/255.255.255.192 and 192.1.1.192.0/255.255.255.192 will no
longer result in a warning message.

IP Filter enhancements:

The 6611 Config Tool now allows the user a capability to filter
TCP/UDP traffic (via TCP/UDP port) uni_directional on IP inbound
filtering.

Previously, the user could only specify TCP/UDP port filtering
bi_directionally. TCP/UDP port filtering is performed on
both TCP/UDP source and destination ports. With this PTF, the
user can further specify filtering on only TCP/UDP source
port or destination port in addition to existing bi_directional
TCP/UDP port filtering.

  ---- End of README file ----

